Codecov Report

❗ No coverage uploaded for pull request base (edge@aa6eba8). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             edge    #6245   +/-   ##
=======================================
  Coverage        ?   79.63%           
=======================================
  Files           ?      206           
  Lines           ?    18687           
  Branches        ?        0           
=======================================
  Hits            ?    14881           
  Misses          ?     3806           
  Partials        ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa6eba8...3c5a907. Read the comment docs.

Wow, thanks so much for this @theosanderson !! This looks like a pretty good, concise overview of the system architecture to me!

We'll chat about this when everyone is back in the office on Monday and get back to you with some comments. Thanks again for pulling this together. It's been on the list for a long time 😅

Make format is still a todo - will post when done

@theosanderson

1. As others have said: this is awesome; thank you so much; we love you.

2. I left lots of little suggestions above.

3. This is well-timed. I met with @sfoster1 and @amitlissack recently to brainstorm what we would want in a document like this. There's a lot of overlap between what we came up with and what you came up with, but also some differences.

   Here are our notes from that meeting. As an "outsider," do you see anything in this list that strikes you as particularly worthy of inclusion, or not worthy of inclusion?

   Of course, we don't necessarily have to make any more big changes in this PR. If you think something is missing, we can note it and come back to it later.

Hey @SyntaxColoring (and @sfoster1 ) , thanks both so much for all of these great changes. As I said at the top I really wouldn't have minded if you rejected the PR entirely so please don't feel under any pressure to take this over what you were already planning!

It's great to hear that there was already a plan to pull this together. There's lots of great stuff in that Google doc.

I would really like to see here:

• how to remount the filesystem for read-write access (something I don't know how to do)
• all the other stuff written from the lens of a Linux user
• link to HTTP endpoint documentation
• (as mentioned above my instinct is that documenting, even unofficially and with warnings, a way of connecting the robot by ethernet would be useful)
• once Eventlog causes hang in build buildroot#87 is addressed I think discussing that additional packages can be selected in buildroot could be good.

I think this PR should now be good for CI. (Let's see). If so I think it could be merged and additional stuff could be part of a future CL when you've had some time to think about details?

Something else that would be good to document sometime is how calibration works at a high level. My understanding is that deck calibration creates a mapping from deck to smoothie coordinates to adjust for non-squareness, etc. Then pipette calibration makes sure the pipette actually knows where it is in Deck coordinates. Then labware calibration essentially adjusts for errors in the labware definition ? Because labware calibration is not per slot?

Agreed that we should expand it further, but this is absolutely a great start.

Awesome :) Thanks folks

Coming into this a bit late (sorry!), but when I first joined Opentrons I made a small doc describing the system architecture as I saw it back then. Ping @SyntaxColoring might be helpful for the doc you're making! I'm also happy to help write up anything about the Protocol Designer side if that's in scope for this project.